Conversation
Singular form is more consistent — `file.viteConfig` reads better than `files.viteConfig` since each property refers to a single file. Prep for community add-on improvements.
🦋 Changeset detectedLatest commit: 5fdc1b4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
files to filefile, isKit, directory
manuel3108
left a comment
There was a problem hiding this comment.
I fully agree with file, totally makes snese.
But having directory.routes in a non kit project is irritating for me. But I do agree that is isKit makes more sense than checking kit against undefined. Undecided and without better ideas on this one.
Feel free to do with this whatever you want :D
Me too :D But it was "simple". Maybe I should have just added a "good" WDYT like this? I'm hesitant with this or just |
manuel3108
left a comment
There was a problem hiding this comment.
Apart from my very minor comment, looks good!
Singular form —
file.viteConfigreads better thanfiles.viteConfigsince each property refers to a single file path.Pure mechanical rename, no logic changes.
Prep for community add-on improvements.
I'm thinking also to switch:
to
So that directory has good default in non-kit as well!